Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed wakeup bug in NioOutboundPipeline #14831

Conversation

pveentjer
Copy link
Contributor

@pveentjer pveentjer commented Apr 3, 2019

Fixes #14830.

Copy link
Member

@kwart kwart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a minor comment WRT backward compatible probe values. Otherwise LGTM.

@mmedenjak mmedenjak modified the milestones: 3.12, 3.13 Apr 3, 2019
@pveentjer pveentjer force-pushed the v3.12/fix/wakeup-bug-NioOutboundPipeline branch from f3acbac to 4d8d274 Compare April 4, 2019 07:05
@pveentjer
Copy link
Contributor Author

I have addressed your comment @kwart . Can you have another look?

private long isScheduled() {
return scheduled.get() ? 1 : 0;
private long scheduled() {
return scheduled.get().ordinal();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is rather unconventional. Any reason we can't use something like return scheduled.get() == State.SCHEDULED ? 1 : 0?
I'm thinking if someone changes the order. The value of this method returns as well.

@mmedenjak mmedenjak merged commit 05b0eab into hazelcast:master Apr 4, 2019
@pveentjer pveentjer deleted the v3.12/fix/wakeup-bug-NioOutboundPipeline branch April 4, 2019 13:21
@mmedenjak mmedenjak modified the milestones: 3.13, 4.0 Apr 17, 2019
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Outbound pipeline is not wake-up properly after merging the write-through changes
3 participants